Computer Systems: A Programmer's Perspective (Global Edition): The 'Everything is a File' Abstraction

In Linux, the "Everything is a File" abstraction maps all I/O sources—from regular files to network sockets—to a uniform stream of bytes. This unified interface allows a consistent System-Level I/O to manage a server process and client process transaction across multi-core processors.

The Unified Model

Whether a program accesses a Regular file, Directory, or hardware like a network adapter, it uses the same primitives. As seen in Hardware organization (Figure 11.2), the OS bridges the CPU and memory to devices via the I/O bus, treating the network as a file to simplify concurrency on multi-core processors.

Robust I/O and Metadata

To handle Short Counts (where requested bytes $k$ relate to available bytes $m$ as $k \ge m$), the Rio (Robust I/O) package provides rio_readinitb for Buffered Input. Metadata is managed via stat, while permissions like O_RDWR and S_IROTH are constrained by the umask.

TERMINAL bash — 80x24

> Ready. Click "Run" to execute.

QUESTION 1

What is the output of a program that opens 'foo.txt' (getting fd 3), closes it, then opens 'baz.txt'?

$fd2 = 3$

$fd2 = 4$

$fd2 = 0$

Segmentation Fault

QUESTION 2

If a disk file 'foobar.txt' contains 'foobar' and a process forks after opening it, what is the output if both parent and child read 1 byte?

Both read 'f'

One reads 'f', the other reads 'o'

Both read 'fo'

The child gets an error

QUESTION 3

Which constant represents opening a file for both reading and writing?

O_RDONLY

O_WRONLY

O_RDWR

S_IROTH

QUESTION 4

What is a 'Short Count' in the context of Unix I/O?

A file with zero bytes.

When read() or write() transfers fewer bytes than requested.

A limited number of file descriptors.

A CPU clock cycle error.

QUESTION 5

How does the OS manage the network adapter in the 'Everything is a File' model?

It bypasses the I/O bus entirely.

It maps the adapter to a socket descriptor.

It treats it as a CPU register.

It uses a special network-only language.

Module Case Study: The Robust I/O Redirector

Implementing Redirection and Buffered Reads

A developer is tasked with redirecting the standard input of a process to a log file 'input.log' and then reading the file using the Rio (Robust I/O) package to ensure no data is lost due to short counts on a high-concurrency multi-core system.

1. Which system call would you use to redirect standard input (descriptor 0) to a new file descriptor 'fd'?

Solution:
You would use dup2(fd, STDIN_FILENO);. This call atomically closes descriptor 0 (if open) and copies the entry of 'fd' into descriptor 0, effectively redirecting the input stream.

2. Why is 'Rio buffered reading' preferred over standard read() when dealing with network sockets?

Solution:
Rio buffered reading (using rio_readinitb and rio_readlineb) reduces system call overhead by copying text lines from an internal buffer. Most importantly, it robustly handles 'short counts' common in network transactions where read() might return before receiving all requested bytes.

Solution:
The final permissions will be 0644 (S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH). The umask 022 masks out the write permissions for 'group' and 'others', ensuring the file is not globally writable despite the open() flags.